Configuration Package
A Configuration Package in Oracle Insurance Rules Workbench is used to group and manage rule changes and related configuration items. Each configuration item (such as rules, transactions, or filters) must be associated with a configuration package before it can be checked in and saved to the database.
Creating a Configuration Package
Configuration packages can be created in one of two ways:
-
Option 1: Manually from the Release Management section, before assigning items.
-
Option 2: During the check-in process while editing a configuration item.
Option 1: Create from Release Management
This method allows a configuration package to be created prior to associating any items.
-
Expand the Release Management folder in the Navigation Explorer.
-
Select the Configuration Packages folder.
-
In the right panel’s toolbar, click the Add Package icon.
-
Enter a name for the configuration package.
-
Click the Save icon next to the name.
-
The new package will appear under Release Management | Configuration Packages with a status of Open.
-
The configuration panel displays the current package status, which can include:
-
Open
-
Ready to Migrate
-
Added for Migration
-
Migrated Configuration Packages
-
On Hold
-
-
Click the three-dot menu (⋯) next to the status field for additional actions, such as:
-
Ready to Migrate: Sets the package to Ready to Migrate.
-
Put on Hold: Releases all items from the package.
-
Add Non-Palette Items: Enter stored procedure details and click Attach.
-
Note: Items in a config package remain locked until they are either checked in as Ready to Migrate or placed On Hold.
Option 2: Create During Rule Check-Out
Any configuration item in draft or edit state must be associated with a configuration package before it can be checked in.
During check-in, a configuration package can be:
-
Selected from the existing list, or
-
Created as a new package using the Add Package option.
Steps to Create or Select a Configuration Package
-
In the configuration panel for the item being edited, click the Config Package dropdown at the top of the panel.
-
To use an existing package, select one from the dropdown list.
-
To create a new package:
-
Click the Add Package icon
next to the dropdown. -
Enter a name for the new configuration package.
-
Click the Save icon.
-
-
Click Check-In
to save the configuration item to the database and associate it with the selected or newly created package. -
If no configuration package is selected at the time of check-in, an error message will appear: Please select a Package.
Viewing Items in a Configuration Package
Once items are checked in or associated with a configuration package, they can be viewed through the following steps:
-
Navigate to Release Management | Configuration Packages in the Navigation Explorer.
-
Select the required configuration package.
-
The Configuration Panel displays a structured view of the package’s contents. Expand the package node to view folders grouped by item type—such as Business Rules, Stored Procedures, or other configuration types.
-
Each folder contains the configuration items that have been included in the package.
Note: Visibility of configuration packages is controlled by security privileges. Users may see only the packages they have created, or all packages in the system, depending on their permissions.
Removing an Item from a Configuration Package
To remove a configuration item from a configuration package
-
Navigate to Release Management | Configuration Packages.
-
Expand the relevant package in the configuration panel and locate the configuration item.
-
Right-click the item and select Remove From Package.
-
When prompted, confirm the action. "Are you sure you want to remove this item from the configuration package?"
-
(Optional) Assign the removed item to another configuration package. Use a distinct name (e.g., “Orphan”) to help manage unassigned items.Configuration items cannot be removed from a package after the package has been migrated.
Note: Configuration items cannot be removed from a package after the package has been migrated.
Note: After configuring the package, add the configuration package to a migration set as part of the release management process.